No, CREST/ESI do not cover all of the XML API. But they cover a lot of it.

The calls are completely different. (The format is JSON rather than XML, for example).

Someone is butt hurt.

Personally, yes it is a bit more in dept than just doing a GET request to an endpoint to get data.

BUT, being able to use tokens for the XML API, being able to open windows using ESI and being able to do things that developers could only dream of with only the XML makes it all worth it.

The convenience of just having people log in like they would into the game and boom have data is much better than having to make an API key, give it to someone and manage all of them.

In addition, dealing with JSON from the ESI/CREST endpoints are much easier to work with than the XML API. XML API by industry standards itself is pretty old. You can read up more on why they decided to do it here: https://community.eveonline.com/news/dev-blogs/introducing-esi/

Personally you are the only one that is against the OAuth that i have come across.

I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.

I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.

C.orporate
C.ontrol
P.ointing

E.veryone's
V.ision
E.lsewhere

Fly Safe everyone o7

Uhhh, you spent time building something, without taking a look at what CCP were going to do? CREST has been out for a fair time now. ESI was announced 2 months ago.

And it's CCP's fault?

CCP's fault? Yes. Now on the other hand If they keep the API system running and keep it updated then I have no problem with new systems coming out and CCP would not need to take any blame. Just keep API's active and running until the end of EVE so newbs like me can make stuff happen.

Being a CSM I would hope you had the guts to bring it up in a meeting and even push hard for it as the majority of the EVE players have little to no knowledge in code.

Another thing to do seeing that you guys want to get rid of API so badly would be to provide tutorials (in full detail) on how the new codes are to be setup/built so newbs like my self can follow along and learn a few things.

Final note and anyone here that plays some of the newer games that have been released in the past 4ish years would likely agree with me. Most of the games being released the past few years are incomplete games full of bugs and interest killers. Now look at CCP they are starting to look just like everyone else. Adding new things to the game and to the coding groups that are incomplete and broken. The players are not your beta testers unless its on the beta server only. When the project is complete then you can release your final product. If you have to push the release date back so be it. Don't be an artist that tries to sale his/her art before your done with it.

PS: Your not the only one out there that needs to do some coding Fuzzworks. There shouldn't be a monopoly on the coding market for anyone making EVE apps, sites, etc.

[quote=Steve Ronuken]hopefully someone will whip up a CLEAR laravel package :)

...

There is no base URL. This isn't CREST which you can walk.

If you're asking 'what is the URL to make requests', you've obviously never actually used the examples on site. Which give you it.

An example:

Go to the ESI site. (That's https://esi.tech.ccp.is/latest/ if you've forgotten)

Pick an API to look at. Lets pick the assets one. So hit show/hide, then click on "Get character assets"

That little exclamation mark in a red circle lets you know you need to have esi-read-assets.v1 as your scope.

So hit the authorize link at the top, select that scope, then scroll down and click authorize.

Go through that auth flow. and it'll return you to the esi site.

Fill in a character ID (your own, as your token is only allowed to read your assets) then click 'try it out'


You'll see something like

curl -i --compressed -X GET --header 'Accept: application/json' --header 'Authorization: Bearer y-CKI1oXOlYF5jjYc1o8-EEQL4OWZeGc_axRU1YdeL32s0MWNzWgT-Jmi1XwULuYLcaqCNpHoDS_T1rwIGTTbw2' 'https://esi.tech.ccp.is/latest/characters/90926985/assets/?datasource=tranquility'

followed by a listing of your assets.

Edit: I've taken out an insult that I shouldn't have put in.

To expand:

Swagger is a specification for APIs. http://swagger.io/ for details

The swagger file, which can be used to automagically generate code, is available at the top of the page. That's the json link.

The link for the 'latest' version of the API is at the top of the page, "URL"

One of the things that drives me nuts is this sso crap. Everyone points to the docs with endpoints and says "its all there" , you know...except and actual working friggen example for php.

A full, complete example to check any authenticated endpoint with this sso garbage. Laravel support?. Anything. One simple example. Show me the light :)

Phealng is great but how long will crest be around? 16months?